Allocation of network resources based on antenna information and/or device type information

ABSTRACT

A device may receive a request, from a user equipment (UE), to connect to a network. The device may receive antenna information indicating that the UE has a single antenna, and the device may receive device type information indicating a device type of the UE or network resource requirements associated with the UE. The device may obtain network policy information, relating to the UE, based on the antenna information and/or the device type information. The network policy information may indicate one or more policy rules associated with allocating network resources. The device may determine a quantity of network resources to allocate based on the network policy information, and the device may allocate the quantity of network resources for the UE.

BACKGROUND

An increasing number of long term evolution (LTE) devices are singleantenna devices. For example, some devices can support only a singleantenna due to size constraints of the devices (e.g., small wearabledevices). Additionally, some devices are designed with a single antennadue to cost concerns (e.g., a device such as an electric meter may notneed two antennas, and designing the electric meter with one antenna maycut costs). Furthermore, other devices use primarily uplink resources(e.g., a surveillance camera that streams data up to a cloud) and, as aresult, do not require more than one downlink antenna.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A and 1B are diagrams of an overview of an example implementationdescribed herein;

FIG. 2 is a diagram of an example environment in which systems and/ormethods, described herein, may be implemented;

FIG. 3 is a diagram of example components of one or more devices of FIG.2; and

FIG. 4 is a flow chart of an example process for allocating networkresources to a device.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The following detailed description of example implementations refers tothe accompanying drawings. The same reference numbers in differentdrawings may identify the same or similar elements.

For category (CAT) 1 LTE devices and higher, the Third GenerationPartnership Project (3GPP) specification defines procedures for dualantenna devices. As a result, a base station (e.g., an evolved Node B(eNB)) may be configured to treat a CAT 1 or higher user equipment (UE)as a dual antenna device. This may cause problems when a base station,communicating with a UE, has to make network resource allocationdecisions. For example, CAT 1 or higher devices may be either singleantenna UEs or dual antenna UEs, and the base station may be configuredto allocate roughly the same amount of network resources to a singleantenna UE as a dual antenna UE.

However, if single antenna UEs have less efficient network resourceusage (e.g., less spectral efficiency) than dual antenna UEs (e.g.,require more network resources to receive the same number of informationbits as compared to dual antenna UEs), then a base station mayinefficiently allocate network resources to these CAT 1 or higherdevices (e.g., by allocating too many network resources to singleantenna UEs, and therefore allocating too few network resources to dualantenna UEs). This may waste network resources (e.g., by allocating toomany network resources to a particular device), cause unfair allocationof network resources, cause handover (HO) failures (e.g., by allocatingtoo few network resources to a particular device), increase the numberof lost connections or dropped calls (e.g., by allocating too fewnetwork resources to a particular device), or the like.

Implementations described herein provide one or more network deviceswith UE antenna information that may be used to create network resourceallocation policies and may be further used to generate network resourceallocation schedules based on the policies. Additionally, oralternatively, the one or more network devices may be provided with UEdevice type information that may be used to create network resourceallocation policies and schedules (e.g., information indicating the typeof device associated with a UE, such as a wearable device type or aninternet of things (IoT) device type).

By receiving antenna information and/or device type information, a basestation is able to make more intelligent network resource allocationdecisions, which conserves network resources by scheduling UEs withresources that are comparable to the particular UE device type. Inaddition, intelligent network resource scheduling decisions improve usersatisfaction and network resource usage by decreasing dropped calls,decreasing handover failures, or the like.

FIGS. 1A and 1B are diagrams of an overview of an example implementation100 described herein. As shown in FIG. 1A, and by reference number 110,a base station may receive a connection request that includes a UEidentifier associated with a UE such as a wearable camera. For example,the UE identifier may be an international mobile equipment identifier(IMEI), and may be sent via a radio resource control (RRC) capabilitiesexchange during the connection request. As shown by reference number120, a home subscriber server/authentication authorization andaccounting server (HSS/AAA) may obtain antenna information and devicetype information using the UE identifier. Here, the HSS/AAA may use theIMEI of the UE to access antenna information and device type informationin a device management database (DMD). The antenna information mayindicate that the UE is a single antenna device. The device typeinformation may indicate that the UE is a wearable camera, and thisparticular type of wearable camera may be associated with using largequantities of uplink resources and small quantities of downlinkresources (e.g., due to the wearable camera being used primarily foruplink streaming).

As shown in FIG. 1B, a policy and charging rules function server (PCRF)may obtain antenna information and device type information from theHSS/AAA. As shown by reference number 130, the PCRF may generate networkpolicy information based on the antenna information and the device typeinformation. The PCRF may send the network policy information back toHSS/AAA, which may send the network policy information to the basestation. In this case, the network policy information may include one ormore rules relating to the allocation of network resources, and the oneor more rules may be associated with the UE being a single antennadevice and a wearable camera. As an example, the PCRF may send a policyrule that reduces the quantity of downlink resources available for theUE (e.g., a wearable camera is likely to use a large quantity of uplinkresources which may result in the PCRF issuing a policy rule thatreduces the quantity of available downlink resources).

As shown by reference number 140, the base station may allocate networkresources to the UE based on the network policy information. As anexample, a scheduler, of the base station, may use the network policyinformation to allocate fewer downlink resources to the UE than atypical dual antenna device. By allocating network resources that arecomparable to the specific resource needs of the UE (e.g., by allocatingjust enough resources to satisfy the specific needs of the wearablecamera), the base station more effectively allocates overall networkresources and increases network capacity.

As indicated above, FIGS. 1A and 1B are provided merely as an example.Other examples are possible and may differ from what was described withregard to FIGS. 1A and 1B. For example, the base station may use thenetwork policy information to allocate network resources for tens,hundreds, or even thousands of UEs.

FIG. 2 is a diagram of an example environment 200 in which systemsand/or methods, described herein, may be implemented. As shown in FIG.2, environment 200 may include a UE 205, a base station 210, an accessnetwork 215, a mobility management entity (MME) 220, a serving gateway(SGW) 225, a packet data network (PDN) gateway (PGW) 230, a HSS/AAA 235,a PCRF 240, a DMD 245, and a network 250. Devices of environment 200 mayinterconnect via wired connections, wireless connections, or acombination of wired and wireless connections.

UE 205 includes one or more devices capable of communicating with basestation 210 and/or a network (e.g., access network 215 and/or network250). For example, UE 205 may include a wearable device (e.g., a camera,smart glasses, a fitness band, or a smart watch), an IoT device, amachine to machine (M2M) device, a wireless communication device, avideo camera, and/or a similar single antenna device. UE 205 maytransmit traffic to and/or receive traffic from base station 210. Insome implementations, UE 205 may transmit to and/or receive traffic frombase station 210 via a RRC capabilities exchange.

Base station 210 includes one or more devices capable of receiving,generating, processing, storing, and/or transmitting network traffic,such as media, audio, video, text, and/or other traffic, destined forand/or received from UE 205. For example, base station 210 may include abase transceiver station, a radio base station, a node B, an eNB, a basestation subsystem, a cellular site, a cellular tower (e.g., a cell phonetower, a mobile phone tower, etc.), a radio access node, a macrocellbase station, a microcell base station, a picocell base station, afemtocell base station, an access point, or a similar type of device.Base station 210 may transfer traffic between UE 205 and network 250 viaan air interface. In some implementations, base station 210 may receive,from HSS/AAA 235 and/or PCRF 240, information identifying network policyinformation associated with UE 205.

Access network 215 includes one or more wired and/or wireless networks.For example, access network 215 may include a cellular network (e.g., a5G network, an LTE network, a 3G network, a code division multipleaccess (CDMA) network, etc.), a public land mobile network (PLMN), awireless local area network (e.g., a Wi-Fi network), a local areanetwork (LAN), a wide area network (WAN), a metropolitan area network(MAN), a telephone network (e.g., the Public Switched Telephone Network(PSTN)), a private network, an ad hoc network, an intranet, theInternet, a fiber optic-based network, a cloud computing network, and/ora combination of these or other types of networks. In someimplementations, access network 215 may allow UE 205 to access one ormore services provided by the evolved packet core (EPC) and/or network250.

MME 220 includes one or more network devices, such as one or more serverdevices, capable of managing authentication, activation, deactivation,and/or mobility functions associated with UE 205. In someimplementations, MME 220 may perform operations relating toauthentication of UE 205. Additionally, or alternatively, MME 220 mayfacilitate the selection of a particular SGW 225 and/or PGW 230 to servetraffic to and/or from UE 205. MME 220 may perform operations associatedwith handing off UE 205 from a first base station 210 to a second basestation 210 when UE 205 is transitioning from a first cell associatedwith the first base station 210 to a second cell associated with thesecond base station 210. Additionally, or alternatively, MME 220 mayselect another MME (not pictured), to which UE 205 should be handed off(e.g., when UE 205 moves out of range of MME 220).

SGW 225 includes one or more network devices capable of routing networktraffic. For example, SGW 225 may include one or more data processingand/or traffic transfer devices, such as a gateway, a router, a modem, aswitch, a firewall, a network interface card (NIC), a hub, a bridge, aserver device, an optical add/drop multiplexer (OADM), or any other typeof device that processes and/or transfers traffic. In someimplementations, SGW 225 may aggregate traffic received from one or morebase stations 210, and may send the aggregated traffic to other networkdevices. SGW 225 may also receive traffic from other network devices,and may send the received traffic to UE 205 via base station 210.

PGW 230 includes one or more network devices capable of providingconnectivity for UE 205 to external packet data networks. For example,PGW 230 may include one or more data processing and/or traffic transferdevices, such as a gateway, a router, a modem, a switch, a firewall, aNIC, a hub, a bridge, a server device, an OADM, or any other type ofdevice that processes and/or transfers traffic. In some implementations,PGW 230 may aggregate traffic received from one or more SGWs 225, andmay send the aggregated traffic to network 250. Additionally, oralternatively, PGW 230 may receive traffic from network 250, and maysend the traffic to UE 205 via SGW 225 and base station 210. PGW 230 mayrecord data usage information (e.g., byte usage, packet usage, etc.),and may provide the data usage information to HSS/AAA 235.

HSS/AAA 235 includes one or more network devices, such as one or moreserver devices, capable of managing (e.g., receiving, generating,storing, processing, and/or providing) information associated with UE205. For example, HSS/AAA 235 may manage information indicating thenumber of antennas associated with UE 205, information indicating adevice type of UE 205 (e.g., a wearable device, an IoT device, a M2Mdevice, etc.), information indicating the network resource requirementsassociated with UE 205, subscription information associated with UE 205,such as information that identifies a profile of a subscriber associatedwith UE 205, information that identifies network services and/orapplications that are accessible to UE 205, location informationassociated with UE 205, a network identifier (e.g., a network address)that identifies UE 205, information that identifies a treatment of UE205 (e.g., quality of service (QoS) information, a quantity of minutesallowed per time period, a quantity of data consumption allowed per timeperiod, etc.), information that identifies whether UE 205 is associatedwith a radio frequency access signaling usage control policy and/or aradio frequency access signaling usage transaction policy, or the like.HSS/AAA 235 may provide this information to one or more other devices ofenvironment 200 to support the operations performed by those devices.

Additionally, or alternatively, HSS/AAA 235 includes one or moredevices, such as one or more server devices that perform authentication,authorization, and/or accounting operations for communication sessionsassociated with UE 205. For example, HSS/AAA 235 may performauthentication operations for a subscriber associated with UE 205 (e.g.,using one or more credentials), may control access, by UE 205, to aservice and/or an application (e.g., based on one or more restrictions,such as time-of-day restrictions, location restrictions, single ormultiple access restrictions, read/write restrictions, etc.), may trackresources used by UE 205 (e.g., a quantity of voice minutes used, aquantity of data used, a quantity of radio frequency signalstransmitted, a quantity of radio access bearers requested and/orestablished, etc.), and/or may perform similar operations.

PCRF 240 includes one or more network devices, such as one or moreserver devices, capable of providing network policies and rules relatingto antenna information and/or device type information. Policies andrules regarding antenna information and/or device type information mayinclude policies and rules indicating network resource requirementsassociated with UEs 205 based on, for example, the number of antennasthe UEs 205 have and/or the device types of the UEs 205. In addition,PCRF 240 may provide network control regarding service data flowdetection, gating, QoS, and/or flow-based charging. Policies and rulesregarding QoS may include policies and rules instructing UE 205 and/ornetwork devices (e.g., base station 210, SGW 225, PGW 230, etc.) tominimize packet loss, to implement a packet delay budget, to provide aguaranteed bit rate (GBR), to provide a particular latency, to reduceradio frequency (RF) signal congestion, and/or to perform otheractivities associated with QoS. PCRF 240 may provide policies and rulesto other network devices, such as base station 210, SGW 225, PGW 230, orthe like, to implement network control. PCRF 240 may determine how acertain service data flow shall be treated, and may ensure thatsubscriber plane traffic mapping and QoS is in accordance with asubscriber's profile and/or network policies.

DMD 245 includes one or more network devices that gather, process,search, store, and/or provide information to other network devices(e.g., HSS/AAA 235, PCRF 240, etc.). For example, DMD 245 may include adatabase that stores information associated with UE 205 and/or otheruser devices, such as antenna information (e.g., a number of antennas,such as single antenna, dual antenna, etc.), device type information(e.g., a device type, such as a wearable device, an IoT device, an M2Mdevice, or the like), information indicating network resourcerequirements associated with the number of antennas and/or the devicetype, and model information (e.g., model type information, model numberinformation, model name information, screen form factors, etc.). In someimplementations, DMD 245 may receive, from HSS/AAA 235, a DMD query(e.g., to determine antenna information associated with UE 205) based ona UE 205 identifier, and may compare the DMD query to the database ofantenna information. Based on the query, DMD 245 may provide antennainformation back to HSS/AAA 235.

Network 250 includes one or more wired and/or wireless networks. Forexample, network 250 may include a cellular network (e.g., a long-termevolution (LTE) network, a code division multiple access (CDMA) network,a 3G network, a 4G network, a 5G network, another type of advancedgenerated network, etc.), a public land mobile network (PLMN), a localarea network (LAN), a wide area network (WAN), a metropolitan areanetwork (MAN), a telephone network (e.g., the Public Switched TelephoneNetwork (PSTN)), a private network, an ad hoc network, an intranet, theInternet, a fiber optic-based network, a cloud computing network, or thelike, and/or a combination of these or other types of networks.

The number and arrangement of devices and networks shown in FIG. 2 areprovided as an example. In practice, there may be additional devicesand/or networks, fewer devices and/or networks, different devices and/ornetworks, or differently arranged devices and/or networks than thoseshown in FIG. 2. Furthermore, two or more devices shown in FIG. 2 may beimplemented within a single device, or a single device shown in FIG. 2may be implemented as multiple, distributed devices. Additionally, oralternatively, a set of devices (e.g., one or more devices) ofenvironment 200 may perform one or more functions described as beingperformed by another set of devices of environment 200.

FIG. 3 is a diagram of example components of a device 300. Device 300may correspond to UE 205, base station 210, MME 220, SGW 225, PGW 230,HSS/AAA 235, PCRF 240, and/or DMD 245. In some implementations, UE 205,base station 210, MME 220, SGW 225, PGW 230, HSS/AAA 235, PCRF 240,and/or DMD 245 may include one or more devices 300 and/or one or morecomponents of device 300. As shown in FIG. 3, device 300 may include abus 310, a processor 320, a memory 330, a storage component 340, aninput component 350, an output component 360, and a communicationinterface 370.

Bus 310 includes a component that permits communication among thecomponents of device 300. Processor 320 is implemented in hardware,firmware, or a combination of hardware and software. Processor 320includes a central processing unit (CPU), a graphics processing unit(GPU), an accelerated processing unit (APU), a microprocessor, amicrocontroller, a digital signal processor, a field-programmable gatearray (FPGA), an application-specific integrated circuit (ASIC), oranother type of processing component. In some implementations, processor320 includes one or more processors capable of being programmed toperform a function. Memory 330 includes a random access memory (RAM), aread only memory (ROM), and/or another type of dynamic or static storagedevice (e.g., a flash memory, a magnetic memory, and/or an opticalmemory) that stores information and/or instructions for use by processor320.

Storage component 340 stores information and/or software related to theoperation and use of device 300. For example, storage component 340 mayinclude a hard disk (e.g., a magnetic disk, an optical disk, amagneto-optic disk, and/or a solid state disk), a compact disc (CD), adigital versatile disc (DVD), a floppy disk, a cartridge, a magnetictape, and/or another type of non-transitory computer-readable medium,along with a corresponding drive.

Input component 350 includes a component that permits device 300 toreceive information, such as via user input (e.g., a touch screendisplay, a keyboard, a keypad, a mouse, a button, a switch, and/or amicrophone). Additionally, or alternatively, input component 350 mayinclude a sensor for sensing information (e.g., a global positioningsystem (GPS) component, an accelerometer, a gyroscope, and/or anactuator). Output component 360 includes a component that providesoutput information from device 300 (e.g., a display, a speaker, and/orone or more light-emitting diodes (LEDs)).

Communication interface 370 includes a transceiver-like component (e.g.,a transceiver and/or a separate receiver and transmitter) that enablesdevice 300 to communicate with other devices, such as via a wiredconnection, a wireless connection, or a combination of wired andwireless connections. Communication interface 370 may permit device 300to receive information from another device and/or provide information toanother device. For example, communication interface 370 may include anEthernet interface, an optical interface, a coaxial interface, aninfrared interface, a radio frequency (RF) interface, a universal serialbus (USB) interface, a Wi-Fi interface, a cellular network interface, orthe like.

Device 300 may perform one or more processes described herein. Device300 may perform these processes in response to processor 320 executingsoftware instructions stored by a non-transitory computer-readablemedium, such as memory 330 and/or storage component 340. Acomputer-readable medium is defined herein as a non-transitory memorydevice. A memory device includes memory space within a single physicalstorage device or memory space spread across multiple physical storagedevices.

Software instructions may be read into memory 330 and/or storagecomponent 340 from another computer-readable medium or from anotherdevice via communication interface 370. When executed, softwareinstructions stored in memory 330 and/or storage component 340 may causeprocessor 320 to perform one or more processes described herein.Additionally, or alternatively, hardwired circuitry may be used in placeof or in combination with software instructions to perform one or moreprocesses described herein. Thus, implementations described herein arenot limited to any specific combination of hardware circuitry andsoftware.

The number and arrangement of components shown in FIG. 3 are provided asan example. In practice, device 300 may include additional components,fewer components, different components, or differently arrangedcomponents than those shown in FIG. 3. Additionally, or alternatively, aset of components (e.g., one or more components) of device 300 mayperform one or more functions described as being performed by anotherset of components of device 300.

FIG. 4 is a flow chart of an example process 400 for allocating networkresources to a device. In some implementations, one or more processblocks of FIG. 4 may be performed by base station 210. In someimplementations, one or more process blocks of FIG. 4 may be performedby another device or a group of devices separate from or including basestation 210, such as UE 205, MME 220, SGW 225, PGW 230, HSS/AAA 235,PCRF 240, or DMD 245.

As shown in FIG. 4, process 400 may include receiving antennainformation indicating that a user equipment (UE) has a single antenna(block 410). In some implementations, base station 210 may receiveantenna information, from UE 205, indicating that UE 205 includes asingle antenna. Additionally, or alternatively, base station 210 mayreceive antenna information, indicating that UE 205 includes a singleantenna, from a network device, such as MME 220, HSS/AAA 235, PCRF 240,or DMD 245.

In some implementations, base station 210 may receive antennainformation from UE 205 during or after a connection request. As anexample, UE 205 may send antenna information to base station 210, duringa connection request, indicating that UE 205 is a single antenna device.During the connection request, UE 205 and base station 210 mayparticipate in a RRC capabilities exchange where UE 205 may send (e.g.,as a parameter in the RRC capabilities exchange) antenna information tobase station 210. Base station 210 may send the antenna information toanother network device (e.g., HSS/AAA 235, PCRF 240, DMD 245, etc.), andthe other network device may use the antenna information to create andstore policies regarding the allocation of network resources, asdescribed further herein.

In some implementations, base station 210 may receive antennainformation from another network device. For example, HSS/AAA 235 and/orDMD 245 may store antenna information and may send the stored antennainformation to base station 210. HSS/AAA 235 and/or DMD 245 may storethe antenna information in a way that indicates a relationship between aUE identifier (e.g., an IMEI, an international mobile subscriberidentity (IMSI), a subscriber identity module (SIM), an integratedcircuit card identifier (ICCID), etc.) and antenna informationassociated with UE 205.

As an example, base station 210 may receive, from HSS/AAA 235, antennainformation indicating that UE 205 is a single antenna device. In thiscase, during or after UE 205 connects to base station 210, UE 205 maysend base station 210 a UE identifier, and base station 210 may send theUE identifier to HSS/AAA 235. HSS/AAA 235 may use the UE identifier toaccess the antenna information (e.g., information indicating that UE 205is a single antenna device) in a subscriber profile associated with UE205, and HSS/AAA 235 may send the antenna information to base station210.

As another example, base station 210 may receive, from DMD 245, antennainformation indicating that UE 205 is a single antenna device. In thiscase, during or after UE 205 connects to base station 210, UE 205 maysend base station 210 a UE identifier, and base station 210 may send theUE identifier to HSS/AAA 235. HSS/AAA 235 may use the UE identifier toaccess antenna information stored by DMD 245. For example, HSS/AAA 235may use the UE identifier as a search query, and the search query may beused to locate a record, stored by DMD 245, that has a matching UEidentifier along with corresponding antenna information (e.g., antennainformation indicating that UE 205 is a single antenna device). HSS/AAA235 may send the antenna information to base station 210. By providingbase station 210 with information indicating that UE 205 is a singleantenna device, base station 210 is able to make more intelligentnetwork resource allocation decisions, as described further herein.

As further shown in FIG. 4, process 400 may include receiving devicetype information indicating a device type of the UE and/or networkresource requirements associated with the UE (block 420). Device typeinformation may indicate a type of device (e.g., a wearable device, anIoT device, an M2M device, a device with a sensor, an uplink-centricdevice such as a device that consumes primarily uplink resources, etc.),and/or may indicate network resource requirements associated with UE 205(e.g., a device application may be associated with a certain range ofper day data-byte consumption, an amount of throughput, an amount oflatency, an amount of jitter, a level of QoS, etc.). Device typeinformation may be received alone, or in conjunction with, the antennainformation described above.

In some implementations, base station 210 may receive, from UE 205,device type information indicating a device type of UE 205. As anexample, during a connection request from UE 205, base station 210 mayreceive device type information indicating that UE 205 is a wearabledevice. During the connection request, UE 205 and base station 210 mayparticipate in a RRC capabilities exchange where UE 205 may send (e.g.,as a parameter in the RRC capabilities exchange) the device typeinformation to base station 210. Base station 210 may send the devicetype information to another network device (e.g., HSS/AAA 235, PCRF 240,DMD 245, etc.), and the other network device may use the device typeinformation to create and store policies regarding the allocation ofnetwork resources, as described further herein.

Additionally, or alternatively, base station 210 may receive, from UE205, device type information indicating network resource requirementsassociated with UE 205. As an example, during or after a connectionrequest from UE 205, base station 210 may receive device typeinformation (e.g., UE 205 may be a wearable camera) indicating that thedevice type of UE 205 is associated with using a low amount of downlinkresources per day (e.g., a wearable camera may use a low amount ofdownlink resources because wearable cameras are used primarily foruplink streaming).

Additionally, or alternatively, base station 210 may receive, from UE205, a UE identifier, and base station 210 may use the UE identifier toobtain information indicating network resource requirements associatedwith UE 205. As an example, during or after a connection request from UE205, base station 210 may receive a UE identifier, and base station 210may use the UE identifier to obtain information indicating networkresource requirements associated with UE 205. In some cases, basestation 210 may use the UE identifier as a search query, and the searchquery may be used to locate a record, stored by a network device (e.g.,HSS/AAA 235, DMD 245, etc.), that has a matching UE identifier, alongwith corresponding information indicating the network resourcerequirements associated with UE 205. In other cases, base station 210may use the UE identifier to access a local data structure that storesthe UE identifier with corresponding network resource requirementsassociated with UE 205. Base station 210 may also obtain networkresource requirements associated with UE 205 by receiving, from UE 205,information indicating a type of device of UE 205 (e.g., during aconnection request), and may access the information in the same mannerdescribed above.

In some implementations, base station 210 may receive, from a networkdevice such as HSS/AAA 235 or DMD 245, device type informationindicating a device type of UE 205. As an example, a subscriber profileof UE 205 (e.g., stored by HSS/AAA 235) may include informationindicating that UE 205 is a wearable device. In this case, when UE 205sends a UE identifier to base station 210, base station 210 may send theUE identifier to HSS/AAA 235, and HSS/AAA 235 may use the UE identifierto access the information indicating that UE 205 is a wearable device.As another example, the device type information may be stored by DMD245, and accessed by HSS/AAA 235, as described above.

Additionally, or alternatively, base station 210 may receive, from anetwork device such as HSS/AAA 235 or DMD 245, device type informationthat indicates network resource requirements associated with UE 205. Asan example, a subscriber profile of UE 205 (e.g., stored by HSS/AAA 235)may include information indicating that UE 205 uses primarily uplinkresources (e.g., UE 205 may be a wearable camera used primary for uplinkstreaming). In this case, when UE 205 sends a UE identifier to basestation 210, base station 210 may send the UE identifier to HSS/AAA 235,and HSS/AAA 235 may use the UE identifier to access device typeinformation indicating that UE 205 is a wearable camera that usesprimarily uplink resources. As another example, the device typeinformation may be stored by DMD 245 and accessed by HSS/AAA 235, asdescribed above. By providing base station 210 with informationindicating the device type and/or the network resource requirementsassociated with UE 205, base station 210 intelligently allocates networkresources.

As further shown in FIG. 4, process 400 may include obtaining networkpolicy information relating to the UE based on the antenna informationand/or the device type information (block 430). For example, basestation 210 may obtain network policy information relating to UE 205from one or more network devices (e.g., MME 220, SGW 225, PGW 230,HSS/AAA 235, PCRF 240, and/or DMD 245), and the network policyinformation may be based on the antenna information and/or the devicetype information of UE 205. Network policy information may includeinformation indicating one or more policy rules that may be used toallocate network resources to UE 205.

In some implementations, prior to base station 210 obtaining the networkpolicy information, PCRF 240 may use the antenna information and/or thedevice type information to generate the network policy information. Forexample, PCRF 240 may access antenna information and/or device typeinformation stored by a network device such as HSS/AAA 235 and/or DMD245, and PCRF 240 may use the antenna information and/or device typeinformation to generate one or more policy rules that allocate networkresources to UE 205. PCRF 240 may generate one or more policy rules, forexample, by monitoring the network resources that UEs 205 of aparticular device type consume during a given time period. As anexample, PCRF 240 may monitor a volume of network traffic that UEs 205of a particular device type consume during a given time period. In thiscase, PCRF 240 (or a different network device such as HSS/AAA 235 and/orDMD 245) may store information indicating the network traffic consumedby the UEs 205, during the given time period, with corresponding antennainformation and/or device type information. PCRF 240 may send thisinformation to base station 210, and base station 210 may use the one ormore policy rules to allocate network resources to UE 205, as describedfurther herein.

In some implementations, PCRF 240 may generate policy rules thatindicate a situation where base station 210 may reduce a quantity ofnetwork resources available for UE 205 (e.g., a policy rule may indicatea situation where base station 210 may reduce a quantity of uplinkresources and/or reduce a quantity of downlink resources, a policy rulemay indicate a situation where base station 210 may reduce a quantity ofnetwork resources based on a time restriction, a policy rule mayindicate a situation where base station 210 may reduce a quantity ofnetwork resources based on a device priority level, etc.). Additionally,or alternatively, PCRF 240 may generate policy rules that indicate asituation where base station 210 may increase a quantity of networkresources available for UE 205 (e.g., a policy rule may indicate asituation where base station 210 may increase network resources based onone or more QoS parameters, a policy rule may indicate a situation wherebase station 210 may increase network resources based on a degree ofmobility of a device, a policy rule may indicate a situation where basestation 210 may increase network resources based on one or moreexception conditions, such as a critical condition that requiresallocating additional network resources to a device when the criticalcondition is satisfied, etc).

In some implementations, base station 210 may obtain, from the one ormore network devices, network policy information for UE 205 thatindicates one or more policy rules. As an example, one or more policyrules may be associated with UE 205 being a single antenna device suchas a smart meter. In this case, the one or more policy rules may includea policy rule that reduces a quantity of available network resourcesduring periods of heavy network traffic (e.g., a quantity of networktraffic that satisfies a threshold). This policy rule may be created fora device type such as a smart meter because smart meters may beconfigured to transmit data during set intervals, and changing thetransmission interval may be done without any major consequence (e.g.,whether a smart meter transmits data at 6:00 PM or 11:00 PM may notmatter if a user is not checking the data until the following day). As aresult, base station 210 may reduce network resources available to thesmart meter during periods of heavy network traffic, thereby conservingoverall network resources and maximizing operating efficiency of thenetwork.

As another example, base station 210 may obtain one or more policy rulesassociated with UE 205 being a single antenna device such as a wearablecamera. In this case, the one or more policy rules may include a rulethat provides for a reduced quantity of downlink resources, whileproviding for restriction-free use of uplink resources. This policy rulemay be created for a device type such as the wearable camera becausewearable cameras are used primarily for uplink streaming. As a result,base station 210 may reduce downlink resources without restricting theuplink resources needed for the wearable camera to stream data.

As another example, base station 210 may obtain policy rules associatedwith UE 205 being a single antenna device such as a M2M/IoT securitysystem. In this case, the one or more policy rules may include a rulethat reduces a quantity of network resources associated with non-VoLTEtransmissions, while providing for restriction-free use of VoLTE in caseof an emergency (e.g., the security system may need to make a VoLTE callto report a crime). By obtaining policy rules associated with theantenna information and the device type of UE 205, base station 210 isable to make more efficient network resource allocation decisions.

Additionally, or alternatively, PCRF 240 may generate models which aretrained using artificial intelligence or machine learning, and themodels identify policy rules based on the antenna information and/or thedevice type information. For example, assume PCRF 240 monitors andstores the antenna information and/or the device type information of UEs205 that connect to a network (this may be tens, hundreds, or eventhousands of UEs 205). PCRF 240 may use the antenna information and/orthe device type information to generate models that are able to predicta quantity of resources to allocate to a particular UE 205 based on thenetwork resources used by UEs 205 that share the same number of antennasor that share the same device type.

As an example, PCRF 240 may generate a model using antenna informationand/or device type information of UEs 205 that connect to a network(e.g., over a given time period). In this case, the model may, fordifferent groups of UEs 205 (e.g., where a group of UEs 205 isassociated with a particular combination of device type informationand/or antenna information), include information indicating a range ofnetwork resources consumed by the groups of UEs 205. The model may betrained in real-time (e.g., relative to a UE 205 connecting to thenetwork), or PCRF 240 (or another network device such as HSS/AAA 235and/or DMD 245) may store the model for later use.

As further shown in FIG. 4, process 400 may include allocating networkresources for the UE based on the network policy information (block440). For example, a scheduler of base station 210 may allocate networkresources based on the network policy information. The scheduler of basestation 210 may allocate network resources for UE 205 by using one ormore scheduling algorithms to determine one or more network resourcelimitations and/or one or more time limitations associated with UE 205(e.g., a network resource limitation may be a quantity of networkresources to allocate to UE 205, and a time limitation may be a timeperiod where UE 205 may use the quantity of network resources). In someimplementations, base station 210 may determine the one or more networkresource limitations and/or the one or more time limitations for UE 205by considering the network policy information, the antenna information,and/or the device type information. Additionally, or alternatively, basestation 210, when allocating network resources to UE 205, may considernetwork traffic associated with other UEs 205 and/or priorityinformation associated with other UEs 205.

As an example, base station 210 may receive a request to connect to anetwork from a single antenna device such as a smart meter. Assume that,at this same time, base station 210 is receiving heavy network trafficfrom a group of dual antenna devices and/or other single antennadevices. Further assume that the network policy information associatedwith UE 205 includes a policy rule for allocating a reduced quantity ofnetwork resources to the smart meter during periods of heavy networktraffic. Due to heavy network traffic, base station 210 may execute ascheduling algorithm that allocates a reduced quantity of networkresources to the smart meter based on the policy rule. By reducing thequantity of network resources available for UE 205 during periods ofheavy network traffic, base station 210 efficiently allocates networkresources in a way that reduces network congestion.

As another example, base station 210 may receive a request to connect toa network from a single antenna device such as a wearable camera. Assumethat, at this same time, base station 210 may also be receiving trafficfrom a group of dual antenna devices and/or single antenna devices.Further assume that the network policy information associated with UE205 may include a policy rule for allocating a reduced quantity ofdownlink resources (e.g., due to the wearable camera being usedprimarily for uplink streaming). Next, base station 210 may execute ascheduling algorithm that allocates a reduced quantity of downlinkresources to UE 205 based on the policy rule. By reducing the quantityof network resources available to UE 205, base station 210 frees upadditional network resources for other network devices (e.g., such asother UEs 205).

As another example, base station 210 may receive a request to connect toa network from a single antenna device such as a security camera. Assumethat, at this same time, base station 210 may also be receiving trafficfrom a group of dual antenna devices and/or a group of other singleantenna devices. Further assume that the network policy informationassociated with UE 205 may include a policy rule for allocating areduced quantity of network resources to UE 205 for non-VoLTEtransmissions (e.g., without restricting the network resources availablefor VoLTE transmissions in case the security camera needs to report acrime). Next, base station 210 may execute a scheduling algorithm thatallocates a reduced quantity of network resources to UE 205 fornon-VoLTE transmissions. By allocating network resources based onantenna information and device type information, base station 210conserves overall network resources, and improves network resource usageby decreasing dropped calls, reducing handover failures, or the like.

In some implementations, base station 210 may allocate and reallocatenetwork resources for UEs 205 using one or more scheduling algorithmsthat consider the network resource needs of the UEs 205 during aparticular time period (e.g., a period with network congestion, a periodwithout network congestion, etc.). For example, base station 210 mayallocate network resources to a group of single antenna UEs 205, andbase station 210 may subsequently decrease a quantity of networkresources available for the group of single antenna UEs 205 duringperiods of network congestion. As an example, base station 210 maydecrease a quantity of network resources available for a group of singleantenna UEs 205 if new devices connect to the network and cause networkcongestion. By allocating fewer resources to single antenna UEs 205during a period of network congestion, base station 210 is able toallocate additional network resources to dual antenna UEs 205 thatconnect to the network, and this may decrease the number of droppedcalls and handover failures associated with those devices.

In some implementations, base station 210 may monitor single antennadevices separately from dual antenna devices. In this case, base station210 may be able to detect technical problems or deficiencies that arespecific to single antenna devices and may send information indicatingkey performance indicators (KPIs) to one or more network devices who mayperform preventative and/or restorative actions. In this way, basestation 210 makes additional resource-saving decisions based on thenetwork policy information.

Although FIG. 4 shows example blocks of process 400, in someimplementations, process 400 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 4. Additionally, or alternatively, two or more of theblocks of process 400 may be performed in parallel.

By providing one or more network devices with antenna information and/ordevice type information, base station 210 is able to make moreintelligent network resource allocation decisions (e.g., by allocatingUEs 205 with resources that are comparable to the particular device typeof UE 205). In addition, the intelligent network resource schedulingdecisions improve user satisfaction and network resource usage bydecreasing dropped calls, decreasing handover failures, or the like.

The foregoing disclosure provides illustration and description, but isnot intended to be exhaustive or to limit the implementations to theprecise form disclosed. Modifications and variations are possible inlight of the above disclosure or may be acquired from practice of theimplementations.

As used herein, the term component is intended to be broadly construedas hardware, firmware, or a combination of hardware and software.

To the extent the aforementioned embodiments collect, store, or employpersonal information provided by individuals, it should be understoodthat such information shall be used in accordance with all applicablelaws concerning protection of personal information. Additionally, thecollection, storage, and use of such information may be subject toconsent of the individual to such activity, for example, through wellknown “opt-in” or “opt-out” processes as may be appropriate for thesituation and type of information. Storage and use of personalinformation may be in an appropriately secure manner reflective of thetype of information, for example, through various encryption andanonymization techniques for particularly sensitive information.

It will be apparent that systems and/or methods, described herein, maybe implemented in different forms of hardware, firmware, or acombination of hardware and software. The actual specialized controlhardware or software code used to implement these systems and/or methodsis not limiting of the implementations. Thus, the operation and behaviorof the systems and/or methods were described herein without reference tospecific software code—it being understood that software and hardwarecan be designed to implement the systems and/or methods based on thedescription herein.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of possible implementations. In fact,many of these features may be combined in ways not specifically recitedin the claims and/or disclosed in the specification. Although eachdependent claim listed below may directly depend on only one claim, thedisclosure of possible implementations includes each dependent claim incombination with every other claim in the claim set.

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems, and may be used interchangeably with “one or more.” Furthermore,as used herein, the term “set” is intended to include one or more items(e.g., related items, unrelated items, a combination of related andunrelated items, etc.), and may be used interchangeably with “one ormore.” Where only one item is intended, the term “one” or similarlanguage is used. Also, as used herein, the terms “has,” “have,”“having,” or the like are intended to be open-ended terms. Further, thephrase “based on” is intended to mean “based, at least in part, on”unless explicitly stated otherwise.

What is claimed is:
 1. A device, comprising: one or more processors to:receive a request, from a user equipment (UE), to connect to a network;receive antenna information indicating that the UE has a single antenna;receive device type information indicating a type of device of the UE,the type of device of the UE including one of a plurality of devicetypes, each of the plurality of device types having a single antenna forcommunicating with the network; receive information indicating networkresource requirements associated with the type of device of the UE, thenetwork resource requirements indicating: uplink resource usageassociated with the type of device of the UE, and downlink resourceusage associated with the type of device of the UE; obtain networkpolicy information, relating to the UE, based on the antennainformation, the device type information, and the information indicatingnetwork resource requirements, the network policy information indicatingone or more policy rules associated with allocating network resources,the one or more policy rules including a first policy rule identifying alimit on data-byte consumption for the UE,  wherein the limit ondata-byte consumption is based on at least one of the uplink resourceusage or the downlink resource usage, and the one or more policy rulesfurther including at least one of:  a second policy rule causing areduction in allocated uplink resources, or  a third policy rule causinga reduction in allocated downlink resources; determine a quantity ofnetwork resources to allocate based on the one or more policy rules; andallocate the quantity of network resources for the UE.
 2. The device ofclaim 1, where the one or more processors, when receiving the antennainformation, are to: receive the antenna information, from the UE, via aparameter in a radio resource control (RRC) capabilities exchange. 3.The device of claim 1, where the one or more processors, when receivingthe device type information, are to: receive the device typeinformation, from the UE, via a parameter in a radio resource control(RRC) capabilities exchange.
 4. The device of claim 1, where the one ormore processors, when receiving the antenna information or receiving thedevice type information, are to: receive the antenna information or thedevice type information from a network device.
 5. The device of claim 1,where the network policy information includes a policy rule, of the oneor more policy rules, identifying a guaranteed bit rate (GBR) to beprovided to the UE.
 6. The device of claim 1, where the one or moreprocessors, when allocating the quantity of network resources, are to:reduce a quantity of network resources available for the UE.
 7. Thedevice of claim 1, where the one or more processors, when allocating thequantity of network resources for the UE, are to: reduce a quantity ofnetwork resources, available for the UE, to remove a particular quantityfrom being available to the UE; and allocate the particular quantity toone or more UEs other than the UE.
 8. A non-transitory computer-readablemedium storing instructions, the instructions comprising: one or moreinstructions that, when executed by one or more processors, cause theone or more processors to: receive a request, from a user equipment(UE), to connect to a network; receive antenna information indicatingthat the UE has a single antenna; receive device type informationindicating a device type of the UE, the device type of the UE includingone of a plurality of device types, each of the plurality of devicetypes having a single antenna for communicating with the network;receive information indicating network resource requirements associatedwith the device type of the UE, the network resource requirementsindicating: uplink resource usage associated with the device type of theUE, and downlink resource usage associated with the device type of theUE; obtain network policy information based on the antenna information,the device type information, and the information indicating networkresource requirements, the network policy information indicating one ormore policy rules associated with allocating network resources, the oneor more policy rules including a first policy rule identifying a limiton data-byte consumption for the UE,  wherein the limit on data-byteconsumption is based on at least one of the uplink resource usage or thedownlink resource usage, and the one or more policy rules furtherincluding at least one of:  a second policy rule causing a reduction inallocated uplink resources, or  a third policy rule causing a reductionin allocated downlink resources; determine a quantity of networkresources to allocate based on the one or more policy rules; andallocate the quantity of network resources for the UE.
 9. Thenon-transitory computer-readable medium of claim 8, where the one ormore instructions, that cause the one or more processors to receive theantenna information, cause the one or more processors to: receive theantenna information, from the UE, via a parameter in a radio resourcescontrol (RRC) capabilities exchange.
 10. The non-transitorycomputer-readable medium of claim 8, where the one or more instructions,that cause the one or more processors to receive the device typeinformation, cause the one or more processors to: receive the devicetype information, from the UE, via a parameter in a radio resourcescontrol (RRC) capabilities exchange.
 11. The non-transitorycomputer-readable medium of claim 8, where the one or more instructions,that cause the one or more processors to allocate the quantity ofnetwork resources, cause the one or more processors to: increase aquantity of network resources available for the UE.
 12. Thenon-transitory computer-readable medium of claim 8, where the one ormore instructions, that cause the one or more processors to allocate thenetwork resources for the UE, further cause the one or more processorsto: reduce a quantity of network resources available for the UE toremove a particular quantity from being available to the UE; andallocate the particular quantity to one or more UEs other than the UE.13. The non-transitory computer-readable medium of claim 8, where thenetwork policy information includes a policy rule, of the one or morepolicy rules, identifying a guaranteed bit rate (GBR) to be provided tothe UE.
 14. The non-transitory computer-readable medium of claim 8,where: the uplink resource usage indicates a first range of per daydata-byte consumption, and the downlink resource usage indicates asecond range of per day data-byte consumption.
 15. A method, comprising:receiving, by a device and from a user equipment (UE), a request toconnect to a network; receiving, by the device, antenna informationindicating that the UE has a single antenna; receiving, by the device,device type information indicating a device type of the UE, the devicetype of the UE including one of a plurality of device types, each of theplurality of device types having a single antenna for communicating withthe network; receiving, by the device, information indicating networkresource requirements associated with the device type of the UE, thenetwork resource requirements indicating: uplink resource usageassociated with the device type of the UE, and downlink resource usageassociated with the device type of the UE; obtaining, by the device,network policy information, relating to the UE, based on the antennainformation, the device type information, and the information indicatingnetwork resource requirements, the network policy information indicatingone or more policy rules associated with allocating network resources,the one or more policy rules including a first policy rule identifying alimit on data-byte consumption for the UE, wherein the limit ondata-byte consumption is based on at least one of the uplink resourceusage or the downlink resource usage, and the one or more policy rulesfurther including at least one of: a second policy rule causing areduction in allocated uplink resources, or a third policy rule causinga reduction in allocated downlink resources; determining, by the device,a quantity of network resources to allocate based on the one or morepolicy rules; and allocating, by the device, the quantity of networkresources for the UE.
 16. The method of claim 15, where receiving theantenna information and receiving the device type information comprise:receiving the antenna information and the device type information, fromthe UE, via one or more parameters in a radio resource control (RRC)capabilities exchange.
 17. The method of claim 15, where receiving theantenna information and receiving the device type information comprise:receiving the antenna information and the device type information from anetwork device.
 18. The method of claim 15, where the network policyinformation includes a policy rule, of the one or more policy rules,identifying an amount of network resource throughput for the UE.
 19. Themethod of claim 15, where determining the quantity of network resourcesto allocate comprises: determining a quantity of network resources, forthe UE, based on one or more models that are trained using artificialintelligence or machine learning.
 20. The method of claim 15, whereallocating the quantity of network resources for the UE furthercomprises: reducing a quantity of network resources available for the UEto remove a particular quantity from being available for the UE; andallocating the particular quantity to one or more UEs other than the UE.